On-demand transport services

ABSTRACT

A computing system can receive utilization data from computing devices of requesting users. The system can process the utilization data by (i) executing a transit monitoring engine on the utilization data to detect a cluster of requesting users currently being transported by a third-party transit vehicle to an arrival location of the third-party transit vehicle, and (ii) executing a transport coordination engine on the utilization data to determine, for each requesting user in the cluster, an intent of the requesting user corresponding to a probability that the requesting user will utilize the transport service upon arrival at the arrival location of the third-party transit vehicle.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. application Ser. No. 16/791,540, filed on Feb. 14, 2020; which application is hereby incorporated by reference in its entirety.

BACKGROUND

Public transport riders often require additional transport upon arriving at fixed stations to get them to their respective destinations. However, when popular stations experience a mass outflow of riders (e.g., from trains) that require additional transport, traffic congestion and confusion can result in increased delays.

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosure herein is illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings in which like reference numerals refer to similar elements, and in which:

FIG. 1 is a block diagram illustrating an example computing system implementing an on-demand coordinated transport service, in accordance with examples described herein;

FIG. 2 is a block diagram illustrating an example computing device executing one or more service applications for communicating with a computing system, according to examples described herein;

FIG. 3 is a flow chart describing an example method of coordinating transport for transit riders, according to various examples;

FIG. 4 is a flow chart describing an example method of predictive configuration of transport supply at transit egress areas, according to various examples; and

FIG. 5 is a block diagram that illustrates a computer system upon which examples described herein may be implemented.

DETAILED DESCRIPTION

A computing system can implement on-demand transport services in which user intent to utilize the transport service is identified well prior to the start of the user's actual utilization of the transport service. It is contemplated that the earlier a user's intent can be determined and confirmed, the earlier the computing system can optimally arrange transport for the user to a requested destination. Current applications of rideshare services involve a received transport request from a requesting user, which triggers the computing system to identify a set of candidate drivers, and then select a driver from the candidate set to rendezvous with the user and transport the user to a destination. Examples described herein involve the early identification of the user's intent to utilize the service prior to receiving a transport request, which provides the computing system with increased transport supply planning for the service's early intent users.

Certain scenarios enable early intent detection by the computing system, such as when upcoming requesters are currently being transported by third-party transit means, such as planes, trains, ferries, and buses that travel fixed or quasi-fixed routes and include known stopping locations. For example, the computing system can identify that several users are currently riding a train to an end location or stopping location. In certain implementations, the system can store a user profile for each user, comprising historical utilization data that indicates frequent destinations, home locations, work locations, and other historical usage patterns corresponding to the user's utilization of the transport service. In such a scenario, the computing system can perform transport supply shaping techniques for the stopping location of the train and even further down the various paths to the final destinations of the transiting users.

According to various implementations, the computing system can detect the intent to utilize the transport service by detecting, via location data received from the computing devices of a set of users, a cluster of users moving at a given speed and trajectory, indicating a common third-party transit means being currently utilized (e.g., a public bus or train). These location data may be received via an executing application specific to the on-demand transport services. It has been observed that when users interact with such an application, there is a high probability (e.g., 94%) that the user will engage the service by requesting on-demand transport upon arrival. More personalized information stored in the user profile of each user may provide an even greater certainty of whether the user will engage the service at the stopping location of the third-party transit means, and can further indicate transport preferences or aspects such as price sensitivity, time sensitivity, willingness to utilize electric scooters, bicycles, and the like.

The computing system can determine a stopping time of the third-party transit means and “shape” the supply of transport options at the stopping location prior to arrival of the third-party transit means. As used herein, “shaping” the supply of transport at the stopping location means preemptively configuring various transport options to be available at the stopping location based on the distance, estimated time of arrival, and/or other factors such as distance and elevation changes to the final destination of each user, availability of transport providers (e.g., drivers and AVs), availability and location of electric scooters or bicycles, and the preferences or willingness to utilize different modes of transport by the transiting users. The computing system may then perform a transport supply optimization to determine the optimal usage of transport options for the cluster of transiting users having a common egress location (e.g., a train station), and perform collective supply coordination to ensure that the optimal configuration of transport options are available to the transiting users when they arrive.

In performing the transport optimization, the computing system can—for each user—select between carpool, standard rideshare (e.g., single passenger transport), bicycles, electric bicycles, electric scooters, high-capacity vehicles (e.g., vans), and the like. As described, these selections can be made based on the user's preferences, active querying, willingness or permissions, and/or tolerances. In some aspects, these may be predetermined based on a selectable setting on the app, or queried prior to arrival. The computing system may then remotely coordinate the transport for the stopping location (e.g., scooter and/or bicycle drop-off, transport invites to drivers and/or AVs, etc.), and transmit content data to the computing devices of the transiting users to confirm a dedicated transport option at the arrival location for the user to transport the user to an inferred or selected destination.

In certain implementations, the computing system can further coordinate multi-modal transport for transiting users, which can include one or more additional stops between the arrival location of the third-party transit means to the final destination of the user. For example, a user with an extensive commute between the arrival location and final destination can be first matched with a number of carpool riders to a certain location, where the user may be matched with an available electric scooter for transport to the user's destination. Additionally, the computing system can also detect and account for delays in the third-party transit means through timing and supply shaping techniques described herein.

Among other benefits, examples described herein achieve a technical solution to current technical problems experienced in the field of remote, on-demand transport services. In particular, the computing system described herein can remotely monitor transit means—such as trains, buses, planes, ferries, and the like—determine destination intentions of riders of the transit means while in-transit to an egress location, and pre-configure and coordinate on-demand transport modes for the riders when they egress the third-party transit means. In doing so, the computing system described herein can anticipate transport demand at egress locations, such as train stations, bus stations, airports, ferry terminals, and the like, in order to provide seamless transport for transit riders and reduce congestion at such egress locations.

As used herein, a computing device refers to devices corresponding to desktop computers, cellular devices or smartphones, personal digital assistants (PDAs), laptop computers, virtual reality (VR) or augmented reality (AR) headsets, tablet devices, television (IP Television), etc., that can provide network connectivity and processing resources for communicating with the system over a network. A computing device can also correspond to custom hardware, in-vehicle devices, or on-board computers, etc. The computing device can also operate a designated application configured to communicate with the network service.

One or more examples described herein provide that methods, techniques, and actions performed by a computing device are performed programmatically, or as a computer-implemented method. Programmatically, as used herein, means through the use of code or computer-executable instructions. These instructions can be stored in one or more memory resources of the computing device. A programmatically performed step may or may not be automatic.

One or more examples described herein can be implemented using programmatic modules, engines, or components. A programmatic module, engine, or component can include a program, a sub-routine, a portion of a program, or a software component or a hardware component capable of performing one or more stated tasks or functions. As used herein, a module or component can exist on a hardware component independently of other modules or components. Alternatively, a module or component can be a shared element or process of other modules, programs or machines.

Some examples described herein can generally require the use of computing devices, including processing and memory resources. For example, one or more examples described herein may be implemented, in whole or in part, on computing devices such as servers, desktop computers, cellular or smartphones, personal digital assistants (e.g., PDAs), laptop computers, VR or AR devices, printers, digital picture frames, network equipment (e.g., routers) and tablet devices. Memory, processing, and network resources may all be used in connection with the establishment, use, or performance of any example described herein (including with the performance of any method or with the implementation of any system).

Furthermore, one or more examples described herein may be implemented through the use of instructions that are executable by one or more processors. These instructions may be carried on a computer-readable medium. Machines shown or described with figures below provide examples of processing resources and computer-readable mediums on which instructions for implementing examples disclosed herein can be carried and/or executed. In particular, the numerous machines shown with examples of the invention include processors and various forms of memory for holding data and instructions. Examples of computer-readable mediums include permanent memory storage devices, such as hard drives on personal computers or servers. Other examples of computer storage mediums include portable storage units, such as CD or DVD units, flash memory (such as carried on smartphones, multifunctional devices or tablets), and magnetic memory. Computers, terminals, network enabled devices (e.g., mobile devices, such as cell phones) are all examples of machines and devices that utilize processors, memory, and instructions stored on computer-readable mediums. Additionally, examples may be implemented in the form of computer-programs, or a computer usable carrier medium capable of carrying such a program.

System Description

FIG. 1 is a block diagram illustrating an example computing system implementing an on-demand coordinated transport service, in accordance with examples described herein. In various examples, the computing system 100 can include a requestor interface 115 to communicate, over one or more networks 180, with computing devices 195 of requesting users 197. For example, the computing system 100 can communicate via an executing on-demand service application 196 on the computing devices 195 of the users 197 to enable the users 197 to configure and transmit transport requests for on-demand transport services. In various examples, the computing devices 195 of the users 197 can also transmit location data to the computing system 100 to enable the computing system 100 to perform selection optimizations for matching the user with transport providers, such as drivers and autonomous vehicles.

The computing system 100 can also include a provider interface 105 to communicate, over the one or more networks 180, with computing devices corresponding to various transport providers 190 that are available to provide transport services for the requesting users 197 on demand. In various examples, the communications with the various transport providers 190 can correspond to transport invitations and/or repositioning requests to drivers of standard human-driven vehicles, transport instructions to autonomous vehicles, instructions to drivers of high capacity distribution vehicles to drop off or pick up personal transport vehicles (e.g., manual bicycles, hybrid bicycles, electric scooters, etc.), and/or lock and unlock commands to the personal transport vehicles (e.g., for authentication by a particular user 197 to unlock a bicycle or scooter).

According to examples described herein, the computing system 100 can further include a third-party transit interface 125 to communicate, over the one or more networks 180, with third-party transit resources 185 to determine schedules and transit information of entities operating or otherwise monitoring third-party transit means, such as trains, buses, flights, boat ferries, and the like. Such transit information can provide established schedules, routes, and dynamic information, such as delays, construction information, detours, cancelations, etc. to the computing system 100 in order to enable the computing system 100 to plan and configure transport supply at egress locations of the third-party transit means. These egress locations can comprise bus stops, bus stations, train stations, airport terminals, ferry terminals, and the like.

According to various examples, the computing system 100 can include a transit monitor 140 that accesses or otherwise receives the transit information from the third-party transit resources 185 to determine the transit schedules of the third-party transit means throughout a particular region (e.g., a metropolitan area for which the computing system 100 coordinates on-demand transport, such as the Washington D.C.-Baltimore metroplex). In certain implementations, the transit monitor 140 can further receive the location data from the computing devices 195 of the requesting users 197 to, for example, determine whether a cluster of users 197 are currently riding on a third-party transit means, such as a train, and dynamically determine the ETA of the train to any given station at which a cluster of users 197 will disembark.

In one example, the transit monitor 140 can further receive utilization data from the computing devices 195 of the requesting users 197. The utilization data can correspond to the user's current interactions with the executing service application 196, which can indicate a future desire to request transport at an arrival location of the third-party transit means. Specifically, empirical analysis of historical utilization data of users indicates a high conversion rate (e.g., 94%) of users 197 opening the service application 196 on their computing devices 195 and requesting transport, versus users 197 opening the service application 196 and not requesting transport within a certain amount of time (e.g., fifteen minutes). Accordingly, the utilization data from the service application 196 executing on the computing devices 195 of transiting users 197 can provide the transit monitor 140 with a relatively high probability that any user 197 interacting with the service application 196 while in transit will most likely request transport at an arrival location of the third-party transit means.

In certain implementations, when the transit monitor 140 identifies a cluster of users 197 currently in transit on a third-party transit means, the transit monitor 140 can further monitor the user devices 195 for utilization data indicating any user's interactions with the service application 196. In some aspects, when utilization of the service application 196 is detected, the transmit monitor 140 can transmit a utilization trigger to a transport coordination engine 150 of the computing system 100. In further aspects, the transit monitor 140 can process the location data from the computing devices 195 of the cluster of transiting users 197 to update or confirm, at any time, an ETA of the third-party transit means (e.g., a train) to any particular arrival location (e.g., a train station), and transmit the updated ETA information to the transport coordination engine 150.

In one or more examples, upon receiving the utilization trigger from the transit monitor 140, the transport coordination engine 150 can identify the transiting users 197 currently utilizing the service application 196, and transmit a set of transport queries to the user's computing device 195 (e.g., as push notifications via the service application 196) to determine a final destination of the user 197, an arrival location of the third-party transit means at which the user 197 will disembark, and/or a transport preference for transporting the user 197 from the arrival location to the final destination (e.g., a private car, luxury vehicle, carpool, or personal transport). It is contemplated that the transport coordination engine 150 can perform such queries for each transiting user 197 of any third-party transit means throughout the transport service region, in order to perform the transport supply shaping techniques described herein.

It is further contemplated that one or more of the queried notifications can instead be inferred by the transport coordination engine 150. In particular, the computing system 100 can include a database 110 storing user profiles 112 for the requesting users 197. In various applications, the user profile 112 for any particular user 197 can comprise historical utilization data corresponding to the user's historical usage of the on-demand transport service. These data can include common destinations of the user 197 (e.g., a work location, home location, train station, bus station, airport, ferry terminal, etc.), common pick-up locations, commonly used transport services (e.g., scooters, bicycles, standard rideshare, carpool rideshare, etc.), and any default permissions or preferences of the user 197.

In some aspects, the permissions or preferences of the user 197 can indicate a willingness to use personal transport, such as scooters and bicycles (e.g., up to a predefined distance). Additionally or alternatively, the transport coordination engine 150 can query for this information while the user 197 is in transit. Given a current time of day, day of the week, and the route and direction of travel of the third-party transit means, the transport coordination engine 150 can infer an arrival location of the transit means and a final destination of the user 197 using the user's profile 112. In such examples, the transport coordination engine 150 can transmit a simple confirmation query providing the user 197 with the inferred information and asking the user 197 to confirm the arrival location, final destination, and/or transport mode preference.

When the arrival location of the third-party transit means, the final destinations, and the transport permissions or preferences are known for a cluster of the transiting users 197 (hereinafter “cluster data”), the transport coordination engine 150 can provide this information to a transport optimizer 155. As provided above, any portion of the cluster data can be inferred using the historical data in the user profile 112 of any of the transiting users 197 or can be actively queried through the service application 196. The transport optimizer 155 can further receive transport provider information, such as the locations of transport providers (e.g., AVs, carpool drivers, and standard rideshare drivers), the status of each transport provider (e.g., on-trip, available, off-duty), the locations of high capacity distribution vehicles, their inventory of scooters and/or bicycles, and their current distribution schedules (hereinafter “provider data”). The transport optimizer 155 can process the provider data and the cluster data to output optimization results indicating an optimal configuration of transport supply at the arrival location of the third-party transit means.

In various examples, the optimization results can indicate the optimal number or ratio of carpool vehicles, standard rideshare vehicles, electric scooters, bikes, and any other optional transport modes to be sent to and/or available at the arrival location for the transiting users 197 prior to or just after their arrival (e.g., to minimize wait times for the users 197 and/or transport providers 190). For example, with a given ETA of the third-party transit means to the arrival location, the transport optimizer 155 can determine a feasibility of coordinating each of the available transport options to be available when or nearly when the third-party transit means arrives such that the collective wait times of the arriving users 197 is minimized. In variations, the transport optimizer 155 can determine the most optimal configuration of transport modes at the arrival location such that a general or overall logical cost is minimized (e.g., factoring in user and driver wait times, financial cost, transport resource disutility cost of unused scooters, bicycles, and/or drivers, and the like).

In various aspects, the optimization results can further indicate an optimal set of matches between each of the transiting users 197 and the transport options at the arrival location. These matches can include carpool matches of transiting users 197 that have a common route or near-common route to their respective destinations. For carpool matches, the transport optimizer 155 can also account for the capacity of available carpool vehicles. For example, an available medium or high capacity vehicle (e.g., a mini-van or full-sized van) may hold more than three users 197. In such a scenario, the transport coordination engine 150 can identify three or more transiting users 197 with final destinations that align with a particular route, and match these users 197 to the same medium or high capacity carpool vehicle.

The matches can further include a user match to an electric scooter or bicycle in general or an assigned scooter or bicycle, which the computing system 100 can remotely lock or unlock upon authentication by the user 197. In certain implementations, the transport coordination engine 150 can provide the user 197 with a multi-mode form of transport to the user's final destination based on the optimization results. In such implementations, the user 197 may have a common leg of a journey to the user's destination as compared to other transiting users 197, and may be carpool matched to those other users 197 up to an end point of the common leg—at which point the user 197 may be matched to an e-scooter or other personal transport vehicle (PTV) for a remainder of the journey.

Upon receiving the optimization results, the transport coordination engine 150 can coordinate with the various transport providers 190 to be available to provide transport for the transiting users 197 when they arrive. In certain implementations, the transport coordination engine 150 can transmit transport facilitation requests (e.g., instructions and/or invitations) to the computing devices of selected drivers, AVs, and/or drivers of distribution vehicles to configure the transport supply at the arrival location in accordance with the optimization results from the transport optimizer 155. Accordingly, the transport coordination engine 150 can perform supply shaping techniques in a timed manner such that the transport providers 190 are either briefly waiting at the arrival location or en-route to the arrival location when the transiting users 197 disembark from the third-party transit means.

In further implementations, the transport coordination engine 150 can pre-match the transiting users 197 to specified transport providers 190 while the users 197 are in transit (e.g., twenty minutes before arrival). The transport coordination engine 150 may then coordinate with the transport providers 190, providing transport invitations to drivers, and instructing drivers of distribution vehicles to drop-off a certain number of personal transport vehicles at a certain area within the arrival location. When the transit means is near arrival (e.g., within two minutes), the transport coordination engine 150 can update the matches (e.g., accounting for any declined invitations, cancelations by drivers, or delays by any of the transport providers 190), and transmit confirmations of the updated matches to the transiting users 197. The updated matches can indicate a matched transport mode (e.g., a scooter or bicycle), a matched driver and vehicle, a matched carpool vehicle, or matched AV. Upon egressing the transit means, each requesting user 197 can be provided with the match information and/or a granular walking route to travel in order to rendezvous with the matched transport provider 190.

Upon arriving at the arrival location, the third-party transit means may continue traveling to additional arrival locations (e.g., stations, terminals, stops, etc.) carrying additional users 197, which the computing system 100 can continue to perform supply shaping optimization techniques described herein. Thus, it is contemplated that pickup locations at mass transit egress areas—which currently experience significant traffic congestion due to a lack of knowledge of user intent and preemptive planning—can be optimized for reduced or eliminated wait times and significantly reduced traffic congestion. Furthermore, the computing system 100 can perform such supply shaping optimization for any given mass transit egress location within a given transport service region, which can include any bus station, train station, ferry terminal, or airport terminal.

Computing Device

FIG. 2 is a block diagram illustrating an example computing device executing and operating a delivery service application 232 for communicating with a network computing system, according to examples described herein. In many implementations, the computing device 200 can comprise a mobile computing device, such as a smartphone, tablet computer, laptop computer, VR or AR headset device, and the like. As such, the computing device 200 can include telephony features such as a microphone 245, a camera 250, and a communication interface 210 to communicate with external entities using any number of wireless communication protocols. The computing device 200 can further include a positioning module 260 and an inertial measurement unit 264 that includes one or more accelerometers, gyroscopes, or magnetometers. In certain aspects, the computing device 200 can store a designated on-demand transport service application 232 in a local memory 230. In variations, the memory 230 can store additional applications executable by one or more processors 240 of the computing device 200, enabling access and interaction with one or more host servers over one or more networks 280.

The computing device 200 can be operated by a requesting user 197 through execution of the on-demand service application 232. The computing device 200 can further be operated by a transport provider 190 through execution of a provider application 234. For requesting user 197 implementations, the user can select the service application 232 via a user input on the display screen 220, which can cause the service application 232 to be executed by the processor 240. In response, a user application interface 222 can be generated on the display screen 220, which can display available transport options and enable the user to submit a transport request.

For transport provider 190 implementations, the provider 190 can select the provider application 234 via a user input 218 on the display screen 220, which can cause the provider application 234 to be executed by the processor 240. In response, a provider application interface 222 can be generated on the display screen 220, which can enable the provider to receive transport invitations, and accept or decline these invitations. The provider app interface 222 can further enable the transport provider to select a current status (e.g., available, on-duty, on-break, on-trip, busy, unavailable, and the like).

As provided herein, the applications 232, 234 can enable a communication link with a computing system 290 over one or more networks 280, such as the computing system 100 as shown and described with respect to FIG. 1 . The processor 240 can generate user interface features using content data received from the computing system 290 over network 280. Furthermore, as discussed herein, the applications 232, 234 can enable the computing system 290 to cause the generated interface 222 to be displayed on the display screen 220.

In various examples, the positioning module 260 can provide location data indicating the current location of the users and transport providers to the computing system 290 to, for example, enable the computing system 290 to coordinate on-demand transport and implement supply shaping techniques at arrival locations of transit modes, as described herein. In examples described herein, the computing system 290 can transmit content data to the communication interface 210 of the computing device 200 over the network(s) 280. The content data can cause the executing service application 232, 234 to display the respective interface 222 for each executing application 232, 234. Upon selection of a desired transport options by a requesting user, the service application 232 can cause the processor 240 to transmit a transport request to the computing system 290 to enable the computing system 290 to coordinate with transport providers to rendezvous with the users at a selected pickup area and time at the egress location of the transit means.

Methodology

FIGS. 3 and 4 are flow charts describing example methods of coordinating transport for transit riders and preemptive configuration of transport supply at transit egress areas, according to examples described herein. In the below description of FIGS. 3 and 4 , reference may be made to reference characters representing various features of FIGS. 1 and 2 . Furthermore, the processes described with respect to FIGS. 3 and 4 may be performed by an example computing system 100 as shown and described with respect to FIG. 1 . Still further, the processes described with respect to FIGS. 3 and 4 need not be performed in any particular order, and may be combined with other steps shown and described herein.

Referring to FIG. 3 , the computing system 100 can receive utilization data from computing devices 195 of users of an on-demand transport service (300). The computing system 100 may process the utilization data to determine a plurality of the users 197 currently being transported by a third-party transit means, such as a bus, train, or ferry (305). The computing system 100 can determine a final destination of each user 197, where the final destination requires additional transport from an arrival location of the third-party transit means (310).

In various examples, the computing system 100 may then monitor the third-party transit means for supply shaping at the arrival location (315). For example, the computing system 100 can determine and update the ETA of the third-party transit means to account for any delays. In certain examples, transit information from third-party transit resources 185 may be inconsistent with observed transit data from the location data of the transiting users 197. In such examples, the computing system 100 may determine that the transit information received from the third-party transit resources is inaccurate (e.g., stating that the transit means is on-time when the location data indicates a delay), and thus prioritize the observed location information from the computing devices 195 of the transiting users 197. According to examples described herein, the computing system 100 may then implement a transport supply shaping optimization for the arrival location based on the respective destinations of each of the transiting users 197 that are to disembark at the arrival location (320). Specifically, upon confirming the users 197 that are to egress the third-party transit means at the arrival location, the computing system 100 can coordinate with proximate transport providers 190 to create optimal transport supply conditions at the arrival location, in order to, for example, minimize wait times for users 197 and transport providers 190, and improve traffic flow through mass transit egress areas.

FIG. 4 describes a method of detecting early intent to utilize the on-demand transport service while users 197 are in transit, and executing supply shaping techniques at mass egress locations of third-party transit means, according to various examples. Referring to FIG. 4 , the computing system 100 can determine, while the users 197 are in transit, each user's intent to use the on-demand transport service upon disembarking from a third-party transit means (400). For example, the computing system 100 can initially detect a cluster of users 197 moving in a common trajectory using mapping data and positioning data from the computing devices 195 of those users 197 to determine that they are riding a common mass transit vehicle. While the users 197 are transiting, the computing system 100 can detect the launch of the service application 196 on their computing devices 195 and/or any interactions with the service application 196—which can correspond to the utilization data described with respect to FIG. 1 .

In various implementations, the computing system 100 can determine the intent of the transiting users 197 by actively querying the users 197 through communications with their computing devices 195 (402) (e.g., via the service application 196). Additionally or alternatively, the computing system 100 can infer the intent of the transiting users 197 based on historical utilization data (404). In such examples, the computing system 100 can look up historical utilization data in a user profile 112 of each transiting user 197 and determine times of day, days of the week, and common destinations that align with the user's current trajectory on the third-party transit means (e.g., a work location in the early morning on a weekday). In certain implementations, the computing system 100 can make some inferences and/or query transiting users 197 for other information, such as a desired transport option upon arrival, and/or a confirmation of a final destination.

Accordingly, the computing system 100 can either infer or directly query the transiting users 197 for their final destinations, intent to use on-demand transport, transport preferences, and the like (405). In some aspects, during the supply shaping optimization, the computing system 100 can provide suggested multi-mode transport options from the arrival location to the user's final destination, such as a carpool ride from the arrival location to a second location in the direction of travel to the user's final destination, and then a second mode of transport (e.g., an electric scooter) from the second location to the final destination. Prior to, during, and/or after determining the final destinations of the transiting users 197, the computing system 100 can perform a transport supply shaping optimization for a given arrival location of the third-party transit means (410) (e.g., a train station).

As described herein, the optimization can comprise inputs corresponding to the number of transiting users 197 that will disembark from the transit means at the particular arrival location, each user's preferred and/or permitted transport option upon arriving (e.g., standard rideshare, carpool, personal transport, etc.), the final destinations of those users 197, the ETA of the transit means, and the transport supply conditions proximate to the arrival location. These transport supply conditions can correspond to the number of available and/or on-trip transport providers 190 within a certain proximity of the arrival location, the number of available personal transport vehicles (e.g., e-scooters) at the arrival location, and the ETAs of each transport provider 190 and/or personal transport distribution driver to the arrival location.

In various examples, the supply shaping optimization can yield a number or range for an optimal quantity of personal transport vehicles (e.g., scooters or bicycles) for the arrival location (e.g., between fifteen and twenty for a disembarking user base) (415). Upon determining the optimal number or range of personal transport vehicles—and the current number of personal transport vehicles at the arrival location—the computing system 100 can transmit one or more requests to the driver of a distribution vehicle (e.g., a van transporting scooters or bicycles) to place a set number of personal transport vehicles at a designated area of the arrival location (420). In some aspects, the personal transport vehicles can include identification codes or vehicle identification numbers, which the computing system 100 can transmit to matched transiting user 197 to enable the users 197 to identify and unlock a specifically assigned personal transport vehicle (e.g., using a scanned QR code). As described herein, such personal transport vehicles can comprise e-bikes or regular bikes (422) and/or e-scooters or regular scooters (424).

Additionally, the computing system 100 can select and match the transiting users 197 with proximate transport providers 190 and/or personal transport vehicles (425). In certain examples, the computing system 100 can transmit transport invitations or instructions to each of the matched transport providers 190 to arrive at the arrival location of the third-party transit means at or near a particular time associated with the arrival of the transit means (430) (e.g., two minutes after arrival). In certain examples, the computing system 100 can further alleviate traffic congestion at the arrival location by staggering the arrival of transport providers 190, and/or providing different pick-up locations to the users 197 to spread out the traffic into and out of the arrival location. Once the matches are made, the computing system 100 can transmit content data to the computing devices 195 of the transiting users 197 indicating the matched transport provider 190 or a notification to utilize an awaiting personal transport vehicle (435).

Accordingly, the functions of the computing system 100 described herein can more seamlessly integrate mass transit with on-demand transport at any particular egress location. It is contemplated that the supply shaping techniques described herein can be significantly effective for mass transit egress locations of relatively stable transit modes, such as ferries and trains, in which ETAs and user intent can be determined well prior to arrival (e.g., twenty minutes to more than one hour). With knowledge of user intent well prior to arrival, the supply shaping optimizations described herein can achieve various technical as well as practical effects, such as more precise remote coordination of transport, real-time transport and traffic planning and alleviation, and significant overall cost savings due to increased utilization of transport modes.

Hardware Diagram

FIG. 5 is a block diagram that illustrates a computer system upon which examples described herein may be implemented. A computer system 500 can be implemented on, for example, a server or combination of servers. For example, the computer system 500 may be implemented as part of a network service, such as described in FIGS. 1 through 4 . In the context of FIG. 1 , the computer system 100 may be implemented using a computer system 500 such as described by FIG. 5 . The computer system 100 may also be implemented using a combination of multiple computer systems as described in connection with FIG. 5 .

In one implementation, the computer system 500 includes processing resources 510, a main memory 520, a read-only memory (ROM) 530, a storage device 540, and a communication interface 550. The computer system 500 includes at least one processor 510 for processing information stored in the main memory 520, such as provided by a random-access memory (RAM) or other dynamic storage device, for storing information and instructions which are executable by the processor 510. The main memory 520 also may be used for storing temporary variables or other intermediate information during execution of instructions to be executed by the processor 510. The computer system 500 may also include the ROM 530 or other static storage device for storing static information and instructions for the processor 510. A storage device 540, such as a magnetic disk or optical disk, is provided for storing information and instructions.

The communication interface 550 enables the computer system 500 to communicate with one or more networks 580 (e.g., cellular network) through use of the network link (wireless or wired). Using the network link, the computer system 500 can communicate with one or more computing devices, one or more servers, one or more databases, and/or one or more self-driving vehicles. In accordance with examples, the computer system 500 receives requests from mobile computing devices of individual users. The executable instructions stored in the memory 530 can include transit monitoring instructions 522, supply optimization instructions 524, and transport matching instructions 528.

By way of example, the instructions and data stored in the memory 520 can be executed by the processor 510 to implement the functions of an example computing system 100 of FIG. 1 . In various examples, the processor 510 can execute the monitoring instructions 528 to receive location data 586 from requesting users 197 and determine the ETA of a particular third-party transit means, such as a train or ferry. In certain implementations, the processor 510 executes the matching instructions 528 to receive transport requests 584 from requesting users 197, transmitting queries to transiting users 197 matching the users 197 with available transport providers 190. The processor 510 can further execute supply optimization instructions 524, which cause the processor 510 to most optimally configure transport supply at an arrival location of the third-party transit means, given the various factors described herein.

Examples described herein are related to the use of the computer system 500 for implementing the techniques described herein. According to one example, those techniques are performed by the computer system 500 in response to the processor 510 executing one or more sequences of one or more instructions contained in the main memory 520. Such instructions may be read into the main memory 520 from another machine-readable medium, such as the storage device 540. Execution of the sequences of instructions contained in the main memory 520 causes the processor 510 to perform the process steps described herein. In alternative implementations, hard-wired circuitry may be used in place of or in combination with software instructions to implement examples described herein. Thus, the examples described are not limited to any specific combination of hardware circuitry and software.

It is contemplated for examples described herein to extend to individual elements and concepts described herein, independently of other concepts, ideas or systems, as well as for examples to include combinations of elements recited anywhere in this application. Although examples are described in detail herein with reference to the accompanying drawings, it is to be understood that the concepts are not limited to those precise examples. As such, many modifications and variations will be apparent to practitioners skilled in this art. Accordingly, it is intended that the scope of the concepts be defined by the following claims and their equivalents. Furthermore, it is contemplated that a particular feature described either individually or as part of an example can be combined with other individually described features, or parts of other examples, even if the other features and examples make no mentioned of the particular feature. Thus, the absence of describing combinations should not preclude claiming rights to such combinations. 

What is claimed is:
 1. A computing system implementing a transport service, the computing device comprising: a network communication interface to communicate, over one or more networks, with computing devices of requesting users and transport providers utilizing the transport service; one or more processors; and a memory storing instructions that, when executed by the one or more processors, cause the computing system to: receive, over the one or more networks, utilization data from the computing devices of the requesting users, the utilization data corresponding to the computing devices of the requesting users operating an executing application specific to the transport service; process the utilization data by (i) executing a transit monitoring engine on the utilization data to detect a cluster of requesting users currently being transported by a third-party transit vehicle to an arrival location of the third-party transit vehicle, and (ii) executing a transport coordination engine on the utilization data to determine, for each requesting user in the cluster, an intent of the requesting user, the intent corresponding to a probability that the requesting user will utilize the transport service via the executing application upon arrival at the arrival location of the third-party transit vehicle; for each requesting user of the cluster of requesting users, determine a destination that requires additional transport from the arrival location of the third-party transit vehicle; and based on the destination of each requesting user of the cluster of requesting users and the determined intent of each requesting user to utilize the transport service, transmit, over the one or more networks, a set of transport facilitation requests to the computing devices of a selected set of the transport providers to facilitate transport for the cluster of requesting users at the arrival location of the third-party transit vehicle.
 2. The computing system of claim 1, further comprising: a database storing a user profile of each respective user of the cluster of requesting users, the user profile indicating historical utilization information corresponding to historical usage of the transport service by the respective user; wherein the executed instructions cause the computing system to further determine the intent of the respective user to travel to the destination of the respective user by performing a lookup of the historical utilization information in the user profile of the respective user.
 3. The computing system of claim 1, wherein the executed instructions further cause the computing system to: determine, for a first user of the cluster of requesting users, a multi-modal transport plan to transport the first user from the arrival location of the third-party transit vehicle to the destination of the first user; wherein the set of transport facilitation requests enables one or more of the selected set of the transport providers to facilitate the multi-modal transport plan for the first user from the arrival location of the third-party transit vehicle to the destination of the first user.
 4. The computing system of claim 3, wherein the multi-modal transport plan comprises multiple means of transport arranged for the first user from the arrival location of the third-party transport vehicle to the destination of the first user.
 5. The computing system of claim 4, wherein the multiple means of transport comprises a plurality of: a human-driven rideshare vehicle, a shared bicycle, a shared scooter, or an autonomously-driven vehicle.
 6. The computing system of claim 1, wherein the third-party transit vehicle comprises one of a train, a ferry, an airplane, or a bus.
 7. The computing system of claim 1, wherein the utilization data indicates user interactions of each of the requesting users with the service application executing on the computing devices of the requesting users.
 8. A non-transitory computer readable medium storing instructions that, when executed by one or more processors of a computing system, cause the computing system to: communicate, over one or more networks, with computing devices of requesting users and transport providers utilizing the transport service; receive, over the one or more networks, utilization data from the computing devices of the requesting users, the utilization data corresponding to the computing devices of the requesting users operating an executing application specific to the transport service; process the utilization data by (i) executing a transit monitoring engine on the utilization data to detect a cluster of requesting users currently being transported by a third-party transit vehicle to an arrival location of the third-party transit vehicle, and (ii) executing a transport coordination engine on the utilization data to determine, for each requesting user in the cluster, an intent of the requesting user, the intent corresponding to a probability that the requesting user will utilize the transport service via the executing application upon arrival at the arrival location of the third-party transit vehicle; for each requesting user of the cluster of requesting users, determine a destination that requires additional transport from the arrival location of the third-party transit vehicle; and based on the destination of each requesting user of the cluster of requesting users and the determined intent of each requesting user to utilize the transport service, transmit, over the one or more networks, a set of transport facilitation requests to the computing devices of a selected set of the transport providers to facilitate transport for the cluster of requesting users at the arrival location of the third-party transit vehicle.
 9. The non-transitory computer readable medium of claim 8, further comprising: a database storing a user profile of each respective user of the cluster of requesting users, the user profile indicating historical utilization information corresponding to historical usage of the transport service by the respective user; wherein the executed instructions cause the computing system to further determine the intent of the respective user to travel to the destination of the respective user by performing a lookup of the historical utilization information in the user profile of the respective user.
 10. The non-transitory computer readable medium of claim 8, wherein the executed instructions further cause the computing system to: determine, for a first user of the cluster of requesting users, a multi-modal transport plan to transport the first user from the arrival location of the third-party transit vehicle to the destination of the first user; wherein the set of transport facilitation requests enables one or more of the selected set of the transport providers to facilitate the multi-modal transport plan for the first user from the arrival location of the third-party transit vehicle to the destination of the first user.
 11. The non-transitory computer readable medium of claim 10, wherein the multi-modal transport plan comprises multiple means of transport arranged for the first user from the arrival location of the third-party transport vehicle to the destination of the first user.
 12. The non-transitory computer readable medium of claim 11, wherein the multiple means of transport comprises a plurality of: a human-driven rideshare vehicle, a shared bicycle, a shared scooter, or an autonomously-driven vehicle.
 13. The non-transitory computer readable medium of claim 8, wherein the third-party transit vehicle comprises one of a train, a ferry, an airplane, or a bus.
 14. The non-transitory computer readable medium of claim 8, wherein the utilization data indicates user interactions of each of the requesting users with the service application executing on the computing devices of the requesting users.
 15. A computer-implemented method of managing transport, the method being performed by one or more processors and comprising: communicating, over one or more networks, with computing devices of requesting users and transport providers utilizing the transport service; receiving, over the one or more networks, utilization data from the computing devices of the requesting users, the utilization data corresponding to the computing devices of the requesting users operating an executing application specific to the transport service; processing the utilization data by (i) executing a transit monitoring engine on the utilization data to detect a cluster of requesting users currently being transported by a third-party transit vehicle to an arrival location of the third-party transit vehicle, and (ii) executing a transport coordination engine on the utilization data to determine, for each requesting user in the cluster, an intent of the requesting user, the intent corresponding to a probability that the requesting user will utilize the transport service via the executing application upon arrival at the arrival location of the third-party transit vehicle; for each requesting user of the cluster of requesting users, determining a destination that requires additional transport from the arrival location of the third-party transit vehicle; and based on the destination of each requesting user of the cluster of requesting users and the determined intent of each requesting user to utilize the transport service, transmitting, over the one or more networks, a set of transport facilitation requests to the computing devices of a selected set of the transport providers to facilitate transport for the cluster of requesting users at the arrival location of the third-party transit vehicle.
 16. The method of claim 15, further comprising: a database storing a user profile of each respective user of the cluster of requesting users, the user profile indicating historical utilization information corresponding to historical usage of the transport service by the respective user; wherein the one or more processors further determine the intent of the respective user to travel to the destination of the respective user by performing a lookup of the historical utilization information in the user profile of the respective user.
 17. The method of claim 15, further comprising: determining, for a first user of the cluster of requesting users, a multi-modal transport plan to transport the first user from the arrival location of the third-party transit vehicle to the destination of the first user; wherein the set of transport facilitation requests enables one or more of the selected set of the transport providers to facilitate the multi-modal transport plan for the first user from the arrival location of the third-party transit vehicle to the destination of the first user.
 18. The method of claim 17, wherein the multi-modal transport plan comprises multiple means of transport arranged for the first user from the arrival location of the third-party transport vehicle to the destination of the first user.
 19. The method of claim 18, wherein the multiple means of transport comprises a plurality of: a human-driven rideshare vehicle, a shared bicycle, a shared scooter, or an autonomously-driven vehicle.
 20. The method of claim 15, wherein the third-party transit vehicle comprises one of a train, a ferry, an airplane, or a bus. 